release: v1.0.0#25
Merged
Merged
Conversation
Closes the remaining Nice-for-1.0 punch list before tagging v1.0.0:
R22 — ESLint v9 flat-config migration
Replace .eslintrc.json with eslint.config.mjs; drop the legacy
@typescript-eslint/eslint-plugin + parser pair in favour of the
unified typescript-eslint package. Rules carry over verbatim so the
lint result is unchanged on the current src tree (eslint v9 flat
config is the default-and-only format from v9 onward; staying on v8
blocks the v9+ track and widens drift against TS 6 / esbuild 0.28).
.vscodeignore picks up the new config so it stays out of the .vsix.
R29 — Scan-on-save mode
New pipelineCheck.scanOnSave setting (boolean, default false).
When enabled, saving a CI/CD config file triggers a quiet workspace
re-scan via the existing scanWorkspace command — the LSP already
re-publishes diagnostics for the saved file itself on didSave, so
this is purely about catching cross-file effects in *other* CI files
that aren't currently open (a Jenkinsfile that includes the
just-edited shared library, a GHA workflow that calls the
just-edited composite action).
scanWorkspace now takes a { quiet? } option:
- quiet: ProgressLocation.Window (status-bar spinner, no toast,
no cancellation affordance — a scan-on-save run is short enough
that the cancel button isn't a meaningful loss).
- default (user-initiated): ProgressLocation.Notification with
cancellation, completion toast, the existing behaviour.
The save listener in extension.ts gates on providerForPath so only
CI-relevant files trigger a scan, and an in-flight guard collapses
save-storms (autosave, Save All) to a single scan.
Integration test (activation.test.ts) extends the configuration
schema completeness check to cover scanOnSave (and codeLens.enabled
which was already missing).
ROADMAP bookkeeping
- R10, R15 ticked (scan-workspace landed in #19).
- R22 ticked (this commit).
- R29 ticked (this commit).
- Maintainer action items 2 + 3 (Private Vulnerability Reporting,
Discussions) marked enabled — done via the GitHub REST API on
2026-05-19, so SECURITY.md's reporting link and package.json's
qna URL both resolve now.
- Status snapshot row added for the v0.2.0 → 1.0 cycle.
Verification: typecheck + eslint (flat config) + 137-test vitest
suite + integration-compile + bundle smoke all green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Cuts the first stable release. Bumps package.json (and the matching package-lock root) to 1.0.0, folds the CHANGELOG Unreleased block into a ## [1.0.0] — 2026-05-19 section above an empty Unreleased (keeps the awk extractor in publish.yml happy: it prints between the first two `## [` headers, so the GitHub-release body now carries 1.0.0's notes). 1.0.0 is the commitment that the v0.x iteration is done — see the section header in CHANGELOG.md for the substance. Nothing in this commit is functional; the feature work landed in the preceding commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
feat: scan-on-save + ESLint v9 flat-config + roadmap bookkeeping(the closing Nice-for-1.0 punch list) andrelease: v1.0.0(version bump + CHANGELOG fold, no functional changes).v1.0.0onmainto firepublish.yml. The job stalls at theproductionenvironment gate until a reviewer approves; nothing ships to the marketplace or OpenVSX before that click.What's in 1.0.0
.eslintrc.jsonwith eslint.config.mjs; drop@typescript-eslint/eslint-plugin+parserfor the unifiedtypescript-eslintpackage. Rules carry over verbatim (lint result on the currentsrc/is unchanged).pipelineCheck.scanOnSavesetting (defaultfalse). Saves of CI/CD config files trigger a quiet workspace re-scan viascanWorkspace({ quiet: true })—ProgressLocation.Window, no toast, in-flight guard against save-storms. Picks up cross-file effects in other CI files that aren't open (the LSP already handles the saved file itself ondidSave).## [1.0.0] — 2026-05-19above an empty Unreleased block (publish.yml's awk extractor keys on the first two## [headers, so the GitHub release body now carries 1.0.0's notes verbatim).Verification
npm run typecheck✓npm run lint(eslint v9 flat config) ✓npm test— 137 / 137 ✓npm run test:integration:compile✓npm run smoke(bundle activate/deactivate) ✓Test plan
ubuntu-latest,windows-latest,macos-latest(checkjob in ci.yml)xvfb-run+@vscode/test-electron),npm audit --omit=dev --audit-level=high, dogfoodedpipeline-check@v1.0.5action against our own workflows,vsce packagesmokePost-merge
v1.0.0onmainand push the tag — fires publish.yml.productionenvironment gate to releaseVSCE_PAT/OVSX_PATand ship to both registries.🤖 Generated with Claude Code